dsh-openwrite 0.2.8

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,107 @@
+<p align="center">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="assets/logo-dark.svg">
+    <source media="(prefers-color-scheme: light)" srcset="assets/logo-light.svg">
+    <img src="assets/logo-light.svg" width="312" alt="OpenWrite">
+  </picture>
+</p>
+
+<h1 align="center">dsh-Openwrite</h1>
+<p align="center">在 DeepSeek Harness 中规划、写作、审稿和管理长篇小说。</p>
+
+<p align="center">
+  <a href="package.json"><img src="https://img.shields.io/badge/dsh-0.1.2--rc.1-2563eb" alt="dsh 0.1.2-rc.1"></a>
+  <a href="package.json"><img src="https://img.shields.io/badge/Node-%E2%89%A522.19-15803d" alt="Node >= 22.19"></a>
+  <a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache--2.0-0f766e" alt="Apache-2.0"></a>
+</p>
+
+<p align="center">
+  <a href="#快速安装">快速安装</a> ·
+  <a href="#开始使用">开始使用</a> ·
+  <a href="#功能">功能</a> ·
+  <a href="#文档与开发">文档</a> ·
+  <a href="https://github.com/LiPu-jpg/Openwrite/issues">反馈问题</a>
+</p>
+
+这是 [OpenWrite](https://github.com/LiPu-jpg/Openwrite/tree/native-core) 的 dsh 插件版本。
+[DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) 提供 Agent 与交互界面，OpenWrite Core 提供小说领域能力；人物、设定、大纲、正文和评审保存在本地作品目录。
+
+## 快速安装
+
+**0.2.7 标准插件包**兼容 dsh **0.1.2-rc.1**。可下载版本、三平台验收结果和 SHA-256 以 [GitHub Release](https://github.com/LiPu-jpg/Openwrite/releases/tag/v0.2.7) 附件为准；验收方法见 [发布验收](docs/RELEASE_ACCEPTANCE.md)。默认使用 npm `latest` 渠道；商城所需的精确预览版兼容性、验证范围和安装限制见 [DSH STORE 接入](docs/DSH_STORE.md)。
+
+已有匹配版本 dsh 的用户执行：
+
+```sh
+dsh plugin --profile web add -w https://github.com/LiPu-jpg/Openwrite/releases/download/v0.2.7/dsh-openwrite-0.2.7.tgz
+dsh web
+```
+
+也可把这段话交给有终端权限的 Agent：
+
+```text
+请按 https://github.com/LiPu-jpg/Openwrite 的 README 和对应 Release 安装 OpenWrite。
+先核对 Release 验收结果、精确 dsh 版本和 SHA-256，再安装发布的 .tgz。
+已有本地安装先备份并迁移，保留作品、自定义预设、凭据和其他插件。
+启动 dsh web，指导我点击 OpenWrite、准备环境并选择自己的作品。
+不要调用写作模型做安装检查，不要自动升级宿主或放宽 pnpm 构建授权。
+```
+
+首次使用会下载固定版本的 uv、Python 3.12 和锁定依赖，保存在当前 dsh 的专属目录。无需预装 Python，也无需克隆两个分支。目标平台为 macOS arm64/x64、Linux x64、Windows x64；各平台通过情况以发布验收报告为准。模型费用另计。
+
+具体的源码安装、升级、迁移和卸载见 [安装指南](docs/INSTALL.md)。
+
+## 开始使用
+
+1. 执行 `dsh web`，打开它给出的浏览器地址，点击侧栏 **OpenWrite**。等待环境就绪后，选择作品目录。
+2. 入口自动建立 **OpenWrite 创作** 会话；点击 **创作** 即可打开工作台，无需先发消息。对话模型在 dsh 中配置；小说生成与评审模型在「任务 → 模型」配置。
+3. 和 Agent 讨论题材、人物与大纲，确认后再开始写章。已有旧稿可通过「任务 → 导入与导出」接入。
+
+| 日常操作 | 入口 |
+|---|---|
+| 看进度、继续写作 | `/progress`、`/write-next` |
+| 审稿、修改选段 | `/review-chapter`、`/revise-span` |
+| 查伏笔、设定与写法记忆 | `/foreshadow`、`/canon`、`/learn` |
+| 导出成稿 | `/export-book` 或「任务 → 导入与导出」 |
+
+已有会话不会自动切换预设。详细操作与工作区规则见 [使用流程](docs/WORKFLOWS.md)。
+
+## 功能
+
+| 工作环节 | 可以做什么 |
+|---|---|
+| **规划与资料** | 在同一创作会话中整理灵感、人物、世界观、分层大纲与伏笔，维护作品设定。 |
+| **正文创作** | 章节导航、连续审读、正文编辑、选区批注与着色、内部状态/关系标记、自动保存、版本保护与场景结构管理。 |
+| **审稿与修订** | 六域评审、问题定位、修订差异和复评；通过 DAG 查看流程、依赖及证据。 |
+| **模型测试** | 测章节写作或指定范围的大纲设计，多模型独立生成与交叉评审，查看质量、可靠性和费用；候选保存在隔离副本。 |
+| **研究与检索** | 检索作品资料与参考库，管理研究报告、正典和写作记忆。 |
+| **导入与成书** | 旧稿导入、作品迁移、完整备份，以及 Markdown / TXT / EPUB 导出。 |
+
+「创作 / 资料 / 任务」是三个主要工作台。OpenWrite Studio 在本版本中作为领域后端运行，日常操作在 dsh 中完成。
+
+## 文档与开发
+
+| 文档 | 内容 |
+|---|---|
+| [安装指南](docs/INSTALL.md) | Agent 安装步骤、手动安装、模型配置、升级和排错 |
+| [使用流程](docs/WORKFLOWS.md) | Workspace、规划、写章、审稿、修订、导入导出 |
+| [模型测试](docs/BENCHMARK_TASKS.md) | 章节选择、大纲范围、任务 DAG 和结果解读 |
+| [审稿 DAG](docs/REVIEW_DAG_FRAMEWORK.md) | 标准评审框架与证据结构 |
+| [工程说明](docs/DEVELOPMENT.md) | 组件职责、维护命令、调研和改进记录 |
+| [维护手册](docs/PLUGIN_MAINTENANCE.md) · [架构设计](DESIGN.md) | 版本、插件契约、安装维护和跨仓库职责 |
+
+```text
+packages/openwrite-bridge/   小说工具与后端桥接
+packages/studio-panel/       dsh 原生工作台
+presets/openwrite/          OpenWrite 创作预设与技能
+scripts/                   安装、启动、检查与 DoG 适配
+conductor/                 连续写章、评审与修订编排
+```
+
+开发检查：`npm run check:plugin`；跨仓库契约检查：`npm run check`。
+小说核心位于同仓库的 [`native-core` 分支](https://github.com/LiPu-jpg/Openwrite/tree/native-core)，与本分支分别维护。工程进度与验证记录保留在 [GOAL.md](GOAL.md)。
+
+## 许可与来源
+
+项目采用 [Apache-2.0](LICENSE)。`oh-story-*` 技能和随包编辑器保留各自目录中的原有许可证。
+Logo 基于 OpenWrite `native-core` 分支，已调整深浅主题配色；基于 [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness)，图谱集成使用 [dsh-dog](https://github.com/Fun10165/dsh-dog)。

package/THIRD_PARTY_NOTICES.md

@@ -0,0 +1,33 @@
+# Third-party components
+
+OpenWrite is Apache-2.0. The separately maintained Studio panel retains its MIT
+license. DoG is based on Fun10165/dsh-dog v1.2.0, BSD-3-Clause; its full license
+and integration changes are in vendor/dsh-dog/LICENSE and UPSTREAM.md.
+
+The editor ships Vditor and its auxiliary files with the upstream license in
+packages/studio-panel/vendor/vditor/LICENSE. OpenWrite preset skills retain
+their source licenses beside their SKILL.md files.
+
+The release runtime manifest pins uv (MIT/Apache-2.0) and the Astral
+python-build-standalone Python distribution (Python and bundled component
+licenses). Archives are downloaded only on environment preparation and retain
+their license files. URLs and SHA-256 values are in release/runtime-manifest.json.
+
+Python dependency versions and distribution hashes are in release/requirements.lock.
+JavaScript dependency versions, resolved origins and integrity values are in the
+repository lockfiles. Host React, Cordis and dsh services are provided by dsh;
+they are not inlined into the plugin's browser code.
+
+The release includes an OpenWrite-built cryptography 50.0.1 wheel for macOS
+x86_64 because upstream discontinued Intel Mac wheels. It is built from the
+SHA-256 pinned upstream source with statically linked OpenSSL 3.6.3. The wheel
+retains upstream licenses; OpenSSL's full license is in release/wheels/licenses.
+Source hash, toolchain, linkage inspection and the native CI build URL are in
+release/wheels/provenance.json. No cryptography source code was modified.
+
+Intel Macs use the last official ONNX Runtime Intel wheel, 1.23.2; other
+platforms use 1.29.0. Platform markers and distribution hashes are recorded in
+release/requirements.lock and release/platform-overrides.in.
+
+JavaScript runtime dependency license texts are retained in release/licenses,
+with names, versions and upstream repositories in release/source.json.

package/assets/logo-dark.svg

@@ -0,0 +1,31 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="312" height="100" viewBox="0 0 312 100" fill="none" role="img" aria-labelledby="logo-title logo-description">
+  <title id="logo-title">OpenWrite</title>
+  <desc id="logo-description">An open book and quill beside the OpenWrite wordmark. Dark background version.</desc>
+  <defs>
+    <linearGradient id="quill" x1="46" y1="70" x2="80" y2="22" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#8AB6F5"/>
+      <stop offset="1" stop-color="#6398E3"/>
+    </linearGradient>
+    <linearGradient id="wordmark" x1="192" y1="34" x2="302" y2="62" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#8AB6F5"/>
+      <stop offset="1" stop-color="#6398E3"/>
+    </linearGradient>
+  </defs>
+  <g stroke-linecap="round" stroke-linejoin="round">
+    <path d="M20 36C20 28 32 25 50 34C68 25 80 28 80 36V70C80 78 68 81 50 72C32 81 20 78 20 70V36Z" fill="#182433" stroke="#7B91AC" stroke-width="2"/>
+    <path d="M50 34V72" stroke="#7B91AC" stroke-width="1.5"/>
+    <g stroke="#4C6583" stroke-width="1.25">
+      <path d="M26 43C32 40 39 41 45 44M26 52C32 49 38 50 44 53M26 61C32 58 38 59 43 62"/>
+      <path d="M55 44C61 41 68 40 74 43M56 53C62 50 68 49 74 52M57 62C63 59 69 58 74 61"/>
+    </g>
+    <g transform="translate(-10 0) rotate(7 55 50)">
+      <path d="M44 71C47 66 50 58 55 48C61 36 71 26 81 22C79 30 73 40 65 49C60 55 57 60 55 64Q52 69 44 71Z" fill="url(#quill)"/>
+      <path d="M48 67C53 59 60 47 71 33" stroke="#183458" stroke-width="1.35"/>
+    </g>
+    <path d="M194 70C212 68 230 68 248 70C266 72 284 72 302 70" stroke="#5D7FAA" stroke-width="2"/>
+  </g>
+  <g font-family="Georgia, 'Times New Roman', serif" font-size="38" font-weight="700" letter-spacing="-1">
+    <text x="95" y="62" fill="#D9E2ED">Open</text>
+    <text x="192" y="62" fill="url(#wordmark)">Write</text>
+  </g>
+</svg>

package/assets/logo-light.svg

@@ -0,0 +1,31 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="312" height="100" viewBox="0 0 312 100" fill="none" role="img" aria-labelledby="logo-title logo-description">
+  <title id="logo-title">OpenWrite</title>
+  <desc id="logo-description">An open book and quill beside the OpenWrite wordmark. Light background version.</desc>
+  <defs>
+    <linearGradient id="quill" x1="46" y1="70" x2="80" y2="22" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#2464C6"/>
+      <stop offset="1" stop-color="#244FA8"/>
+    </linearGradient>
+    <linearGradient id="wordmark" x1="192" y1="34" x2="302" y2="62" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#2464C6"/>
+      <stop offset="1" stop-color="#244FA8"/>
+    </linearGradient>
+  </defs>
+  <g stroke-linecap="round" stroke-linejoin="round">
+    <path d="M20 36C20 28 32 25 50 34C68 25 80 28 80 36V70C80 78 68 81 50 72C32 81 20 78 20 70V36Z" fill="#F1F5FB" stroke="#7087A3" stroke-width="2"/>
+    <path d="M50 34V72" stroke="#7087A3" stroke-width="1.5"/>
+    <g stroke="#9CABC0" stroke-width="1.25">
+      <path d="M26 43C32 40 39 41 45 44M26 52C32 49 38 50 44 53M26 61C32 58 38 59 43 62"/>
+      <path d="M55 44C61 41 68 40 74 43M56 53C62 50 68 49 74 52M57 62C63 59 69 58 74 61"/>
+    </g>
+    <g transform="translate(-10 0) rotate(7 55 50)">
+      <path d="M44 71C47 66 50 58 55 48C61 36 71 26 81 22C79 30 73 40 65 49C60 55 57 60 55 64Q52 69 44 71Z" fill="url(#quill)"/>
+      <path d="M48 67C53 59 60 47 71 33" stroke="#EAF2FF" stroke-width="1.35"/>
+    </g>
+    <path d="M194 70C212 68 230 68 248 70C266 72 284 72 302 70" stroke="#809BBE" stroke-width="2"/>
+  </g>
+  <g font-family="Georgia, 'Times New Roman', serif" font-size="38" font-weight="700" letter-spacing="-1">
+    <text x="95" y="62" fill="#172435">Open</text>
+    <text x="192" y="62" fill="url(#wordmark)">Write</text>
+  </g>
+</svg>

package/cordis.patch.yml

@@ -0,0 +1,11 @@
+- insert:
+    - id: openwrite-bundle
+      name: dsh-openwrite
+    - id: openwrite-bridge
+      name: dsh-openwrite/bridge
+      config:
+        mode: managed
+    - id: studio-panel
+      name: ./packages/studio-panel/lib/index.js
+    - id: openwrite-dog
+      name: ./vendor/dsh-dog/lib/index.js

package/docs/BENCHMARK_TASKS.md

@@ -0,0 +1,54 @@
+# 模型测试：章节与大纲
+
+在「任务 → 模型测试」先选择测试任务，再选择生成模型和评审模型。
+
+配置页会先显示项目就绪状态。已有正文必须具有有效的接纳基线和当前事实；缺失或过期时会说明原因并禁用开始按钮。测试不会代替作者建立基线或接纳正文。若运行途中失败，后台任务会保留具体错误说明。
+
+## 章节写作
+
+- 「推荐下一章」保留 `next` 语义；下拉列表同时提供真实章纲的 ID、标题和正文状态，可选择其他已规划的待写章。
+- 「输入章节 ID」适合直接定位长大纲中的条目。ID 必须对应可测试章纲；错误 ID 不会静默替换成下一章。
+- 历史章或中间缺章若早于当前正文进度，暂时禁用并说明原因。当前全书事实不能作为历史章的章前状态；本次没有伪造历史事实快照。
+- 保留真实框架和裸写诊断两种模式，以及单章目标字数。
+
+## 大纲设计
+
+- 起点采用全书章号，包含起始章。例如从第 11 章开始设计 3 章，范围就是第 11–13 章。
+- 默认接续现有大纲末尾；可以切换为指定起始章。一次设计 1–20 章，默认 3 章；起点必须晚于现有正文进度，结束章号最多 100000。
+- 大纲使用真实规划器生成连续章纲，再验证结构与编号范围，保存独立候选并进行大纲专项评审。
+- 大纲数量与章节目标字数相互独立。切换任务不会把字数误传为规划数量，也不会沿用裸写诊断模式。
+- 结果分别保留请求范围和实际验证通过的产出范围；没有验证通过的章数显示未知，不根据目标数量补齐。
+
+## DAG 配置与执行证据
+
+`GET /api/benchmarks/options` 是可选目标、任务能力、限制和 DAG 的权威来源。前端不自行拼接另一套执行依赖。
+
+- 章节框架使用章节写作和完整章节评审流程；裸写诊断使用对应的简化写作路径。
+- 大纲使用规划上下文、章纲生成、结构与范围验证、隔离产物保存和专项评审；评审排除正文文风、对白自然度等不适用检查，保留适用的结构、人物、情节、连贯、正典与安全检查。
+- 可展开「智能 DAG 配置」查看节点和依赖。历史记录保存当次配置，之后切换任务不会改写旧配置。
+- 「DAG 执行与证据」展示候选和各评审分支的实际节点状态、依赖、证据路径与摘要。未执行、失败、跳过和部分完成保持各自状态；流程结束不等于质量通过。
+- 测试 DAG 保存在 benchmark 隔离运行中，不替换全局 DoG 或锁定的标准章节评审蓝图。
+
+每个生成模型、重复轮次和评审模型组合使用隔离运行记录，正式大纲和正文不会被测试覆盖。失败候选不进入后续评审；前置依赖未完成时不能启动后继节点。
+
+## 工具调用
+
+`novel_model_benchmark` 增加 `action: "options"`，可先读取可选章节和权威 DAG。
+
+大纲提交示例：
+
+```json
+{
+  "action": "run",
+  "task_type": "outline",
+  "outline_start_chapter": 11,
+  "outline_chapter_count": 3,
+  "execution_mode": "framework",
+  "writer_profile_ids": ["已配置的生成模型 ID"],
+  "reviewer_profile_ids": ["已配置的评审模型 ID"],
+  "repeats": 1,
+  "concurrency": 1
+}
+```
+
+一个评审单元可能包含多个模型调用；界面的候选和评审数量不是底层 API 调用次数。实际模型用量与费用仍以服务端记录为准。

package/docs/COST_MEASUREMENT.md

@@ -0,0 +1,39 @@
+# 小说工具成本比较方法
+
+本文件只定义可复现的测量步骤。UTF-8 工具声明字节数 **不是** tokenizer token，也不是账单费用。没有作者在本会话明确提供的凭据时，真实服务商一行记为 `not-run`。
+
+## 离线（默认，不调用模型）
+
+在隔离环境执行：
+
+```sh
+npm --prefix packages/openwrite-bridge run build
+node --test packages/openwrite-bridge/scripts/tool-policy.test.mjs
+```
+
+`real dsh tool registry isolates 90 tools` 会打印两行 JSON：
+
+| 字段 | 含义 | 不是什么 |
+|---|---|---|
+| `measurement: native-tool-schema` 的 `utf8Bytes` | `JSON.stringify(tools)` 的 UTF-8 字节 | 不是 tokenizer token |
+| `measurement: ptc-presentation` 的 `schemaBytes` | PTC 传输声明的 UTF-8 字节 | 不是缓存命中 |
+| `sdkBytes` | 注入到 system prompt 的 SDK 文本字节 | 不是费用 |
+| `tokenizer: not-measured` | 本仓库不内置某家 tokenizer | 不得改写成已测 token |
+
+同一套检查还断言：普通预设 `novel_*` 为 0；创作预设为 90 且不随 PTC 另一 scope 改变。
+
+要对比「请求大小」，把一次真实 `tools.schemas(agent)` 或 PTC `wireSchemas` 的 JSON 写入文件后对体积做 `wc -c` / SHA-256。这仍是请求体字节，不是 token。
+
+## 真实服务商（需明确授权）
+
+仅当作者在当前会话提供密钥，并且同意产生费用时执行。不要从聊天记录、临时文件或其他应用配置里找密钥。
+
+1. 使用同一创作预设、同一章节、同一提示，分别跑 native 与 PTC（若宿主支持）。
+2. 记录：HTTP 请求体字节、服务商返回的 `usage`（prompt/completion/cache 读写）、账单金额、缓存命中字段（若有）。
+3. 取消一次生成：确认不再调度新请求，已完成候选与用量保留；若服务商请求仍在途，界面保持「取消中」，不得记为已撤回。
+4. 报告分成两块：`offline` 与 `provider`。缺凭据时 `provider.status = not-run`。
+
+## 本任务状态
+
+- 离线 schema 字节：由 tool-policy 测试每次打印。
+- 真实 tokenizer / 缓存命中 / 费用：`not-run`（无本会话授权的模型凭据）。

package/docs/DEVELOPMENT.md

@@ -0,0 +1,65 @@
+# 工程结构与开发文档
+
+[返回首页](../README.md) · [安装指南](INSTALL.md)
+
+为兼容现有安装、审稿产物和浏览器草稿，内部 npm scope、Schema 版本与存储键继续使用
+`@dsh-novel/*` 和 `dsh-novel.*`；这些稳定标识不影响对外产品名。
+
+评审 v2、双 DAG 与模型测试台的跨仓库目标、当前状态和续跑入口统一维护在
+[GOAL.md](../GOAL.md)。后续 Goal 应先读取该文件，并以当前工作树和验证日志为准继续。
+
+- **dsh** 负责 agent 编排：OpenWrite 单一创作预设、技能目录、子代理委派、长上下文压缩
+- **OpenWrite** 负责小说领域能力：规范阅读顺序、稳定场景结构、章节流水线、六域累加评审（兼容 37 项查询）、伏笔 DAG、正典状态
+- **OpenWrite Studio** 在本插件版本中提供无界面的小说领域 HTTP 后端；dsh 是唯一交互壳与编辑工作台
+
+架构与职责划分见 [DESIGN.md](../DESIGN.md)。
+
+## 组件
+
+| 路径 | 说明 |
+|---|---|
+| `packages/openwrite-bridge/` | dsh 插件：90 个 `novel_*` 工具，覆盖 Studio HTTP 动作面并提供隔离模型横评与脱敏 trace |
+| `packages/studio-panel/` | dsh web 原生工作台：创作 / 资料 / 任务，含规范章节导航、连续审读、场景双序、正文编辑器、双 DAG、模型测试台与工具卡 |
+| `presets/openwrite/` | OpenWrite 全流程 agent 预设（规划/资产/写章/评审/修订） |
+| `scripts/install.sh` | 构建插件、安装预设到 `~/.dsh/.agent-presets/`、插件装进 dsh profile |
+| `scripts/dev.sh` | 一键启动 OpenWrite Studio + dsh web |
+| `scripts/verify.sh` | 一键集成验证（服务、领域代理、失效快照、本地编辑器资源、无 iframe） |
+| `conductor/` | Python 编排器：无人值守连续写章 → 六域评审 → 修订/应用/复评闭环（走 OpenWrite 后台任务系统；详见 DESIGN.md §6） |
+
+## 插件开发与维护
+
+建立方法、官方资料、版本升级、安装更新和回退流程见
+[维护手册](PLUGIN_MAINTENANCE.md)。本轮工程维护与模型工作台回归证据见 [GOAL.md](../GOAL.md)。
+
+[标准章节审稿 DAG](REVIEW_DAG_FRAMEWORK.md)：一次定义、逐章实例化的六域 37 项审稿框架。
+开源写作软件、AI 工具和编辑器插件的对照，以及当前产品差距与验收建议，见
+[小说工具调研与改进清单](OPEN_SOURCE_NOVEL_AUDIT.md)。
+用户指定的七个项目的固定版本、源码实现和改进优先级，见
+[七项目专项对照](TARGETED_NOVEL_PROJECT_REVIEW.md)。
+七个框架的社区/源码/测试静态统计、功能成熟度矩阵、各自优势和 OpenWrite 的相对位置，见
+[框架优势与统计](FRAMEWORK_ADVANTAGES.md)。
+基于现状的实施顺序、跨仓库分工、依赖与验收条件见
+[插件完善计划](IMPROVEMENT_PLAN.md)；实际完成状态继续记录在 [GOAL.md](../GOAL.md)。
+S1–S6 之后对照七个外部项目的计划/进行中/已完成，见
+[学习与完善进度](LEARNING.md)（示例书不在目标内）。
+
+```sh
+npm run check:plugin           # 构建、doctor、生命周期、预设、smoke、epochs、组件测试
+npm run check                  # 额外校验相邻 OpenWrite 的共享 contracts
+npm run doctor -- --profiles    # 只读核对本机 web/headless 是否链接本工作树
+```
+
+`check:plugin` 不需要服务、小说或模型凭据，GitHub Actions 也执行此门禁。
+真实系统另跑 `scripts/verify.sh` 和 `npm run test:e2e`；E2E 跳过不算运行时通过。
+
+## DoG 集成
+
+`scripts/install.sh` 默认自动获取固定的 `dsh-dog v1.2.0`，保存到
+`$DSH_HOME/extensions/dsh-dog`，完成构建并只挂载到 web profile；重复运行会复用该目录。
+如需使用已有工作树，可传入 `DSH_DOG_DIR=/path/to/dsh-dog`；明确不安装时设置
+`DSH_DOG_AUTO_INSTALL=0`。
+
+安装器会在缺少 `dog:` 配置时写入安全兜底值。DoG v1.2 优先使用发起调用的 dsh 会话
+Workspace，所以切换作品会自动切换评审/交付图根目录，无需修改 `workspaceRoot` 或重启。
+`novel_review_chapter` 和后台章节评审完成时会自动实例化标准章节审稿 DAG；DoG 只查询
+已物化产物，不会重复调用模型。

package/docs/DSH_STORE.md

@@ -0,0 +1,58 @@
+# DSH STORE 接入
+
+OpenWrite 是一个完整的小说创作插件套件。商城安装目标是仓库根包 `dsh-openwrite`，不是其中的开发子包。
+
+## 唯一安装目标
+
+在商城申请中填写：
+
+- GitHub repository：`https://github.com/LiPu-jpg/Openwrite`
+- Plugin path (optional)：`.`（显式填写，不能留空让扫描器猜测）
+- manifestPath：`package.json`
+- Bundle Patch：`cordis.patch.yml`
+
+根包统一加载 `openwrite-bundle`、`openwrite-bridge`、`studio-panel`、`openwrite-dog`。这些既有 ID 保持稳定。`packages/openwrite-bridge`、`packages/studio-panel` 是内部开发包，不应和根包一起登记到同一个 Profile，也不需要删除它们或拆成独立商城条目。
+
+源码安装必须固定到完整 Commit；`prepare` 会自包含构建三个内部插件，包含 Core wheel、编辑器静态资源、预设和许可证，不依赖相邻源码。构建授权仍遵循用户的 pnpm 设置。普通用户继续优先使用已验收的 GitHub Release `.tgz`，见 README。
+
+## 兼容声明与证据
+
+根 `package.json` 的 `dsh.compatibility.dshReleases` 是精确版本声明；没有实际验证的版本保持 `unknown`。Node.js 下限是 22.19.0，完整基础平台矩阵使用 Node 24，Node 22.19/26 作兼容检查；系统与架构限制见安装指南。
+
+本机 macOS arm64 / Node 24.15 使用 0.2.7 运行代码对 alpha.1 完成了隔离安装、启动、后端初始化、恢复、回退与卸载验证；新版元数据及正式产物另由下述 CI 门禁验证。
+
+alpha 浏览器验收进一步发现 persona 配置由 `text` 改成了必填 `prefix`；预设使用 YAML 锚点将同一份身份文本提供给两个字段，并以两版实际 Config / apply 验证身份只注册一次。
+
+默认宿主仍是 `0.1.2-rc.1`。商城当前滚动窗口还包含 alpha，所以额外验证 `0.1.5-alpha.1`，并保留 `0.1.3-alpha.1`、`0.1.3-alpha.2` 为未知。这不自动升级用户宿主，也不承诺整个 alpha 范围都兼容。
+
+2026-09-09，从官方 npm Registry 直接安装 `@deepseek-ai/dsh@0.1.5-alpha.1` 时，上游范围依赖选中了正在发布的 alpha.2，其中 `@deepseek-ai/dsh-tool-pwsh-persistent@^0.1.5-alpha.2` 当时缺失，安装失败（ETARGET）。兼容测试使用 npm 的 `--before=2026-09-09T00:00:00Z` 解析 alpha.1 发布时的依赖，并保留解析锁。没有修改官方包源码或用 replacements/overrides 冒充官方组件。此证据仅适用于报告中的宿主依赖图，不代表后续浮动依赖安装也通过。
+
+可重复执行的隔离验证：
+
+```sh
+npm install --prefix .tmp-dsh-alpha @deepseek-ai/dsh@0.1.5-alpha.1 --before=2026-09-09T00:00:00Z --registry=https://registry.npmjs.org
+node scripts/release-smoke.mjs dsh-openwrite-<version>.tgz --host-cli=.tmp-dsh-alpha/node_modules/@deepseek-ai/dsh/lib/bin.js
+```
+
+不要把 `<version>` 原样复制；使用待验收的真实包路径。脚本创建临时 DSH_HOME、配置和作品注册表，不读取真实凭据、不调用模型。它验证安装、重复安装、其他插件共存、宿主服务版本、后端准备与认证、中文目录初始化、恢复、失败升级与回退、卸载保留数据；最终报告绑定包 SHA-256 和宿主版本。CI 另执行实际浏览器启动、空会话入口与作品创建，不用页面 HTTP 200 代替这些验证。
+
+`Release artifact validation` 增加独立 alpha.1 Linux/Node 24 任务并保留宿主依赖锁。稳定版原生六平台和源码安装门禁仍保留；最终聚合要求 alpha 与稳定版测试同一个产物。未运行的系统/模型测试不能计为通过。以实际工作流报告为准，兼容声明不是安全审计证明。
+
+## 权限与安装影响
+
+- `prepare`：仅源码安装构建插件，声明在 manifest 中；预编译包已有运行资源。
+- 文件：读写已绑定作品目录；托管环境、缓存和管理记录位于 `$DSH_HOME/openwrite/`，版本化预设位于 `$DSH_HOME/.agent-presets/`。
+- 网络：环境准备从清单中固定来源下载并校验 uv/Python；依赖按锁文件安装。用户发起模型任务时访问其配置的服务。
+- 子进程：启动插件管理的 uv/Python 和回环后端，退出/卸载仅清理自己的进程。
+- 凭据：模型服务配置由宿主管理；准备环境的子进程使用允许列表环境，不继承无关 API Key。工具策略不是操作系统沙箱。
+- 卸载保留作品、凭据和历史；缓存清理是单独操作。旧开发安装按安装指南先备份并迁移，不能同时挂载新旧包。
+
+这些实际能力包括文件写入、网络、子进程和源码构建。不能为了低风险自动收录而隐藏它们、删除核心能力或伪造无权限声明；商城可能需要进一步审核或只提供外部安装入口。目录静态预检、可安装状态、运行验收是不同结果。
+
+## 静态扫描范围
+
+商城扫描器将 DTO 测试中的长英文占位字符串识别为凭据字面量；测试现使用明确的短假值 `test-only` / `test-embedding`，继续验证敏感字段不会进入 DTO。此处没有真实密钥，也没有删除测试。扫描上限仍是 150 个源码文件，仓库文件更多时报告保持“扫描不完整”；子进程和编辑器运行时代码能力继续披露，不能把有界扫描称为完整安全审核。
+
+## 复检
+
+对应 [作者修复请求 #682](https://github.com/AI-Scarlett/DSH-Store/issues/682)。新版固定 Commit 合入默认分支后，用明确的根目录提交预检，并核对商城最新结果。只在其公开结果明确通过后称为“已收录”；提交成功不能冒充审核成功。